Brev 9032/add nebius live capacity#123
Draft
kirtiip20 wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Nebius GPU instance types showed as available in the Brev UI based on tenant quota alone, even when Nebius had no on-demand capacity in that region. Users could select such a type (e.g. 8× H200, L40s) and the launch would then fail at provisioning time.
Root cause
Availability was computed only from tenant quota allowances (a region-specific compute.instance.gpu.* quota check), with no check against the provider's actual capacity. A tenant can hold quota in a region where Nebius currently has no capacity available so the type was still marked available and failed on launch.
Fix
Integrated the Nebius Capacity Advisor (ResourceAdvice) API so availability reflects real-time on-demand capacity & tenant quota:
Remaining tenant quota.
Treated DATA_STATE_UNKNOWN and AVAILABILITY_LEVEL_LIMIT_REACHED as unavailable capacity